Recognize RAM payload USB devices on Linux - #13

On Linux, a RAM payload using the USB helper's 05ac:4144 endpoint is discovered as other, so orchard exec, push and pull refuse to connect. Add the missing ram PID mapping, matching the existing Darwin discovery behavior.

The regression fixture checks the mode, boot identity, serial endpoint and absence of an ECID for this RAM gadget.

Validation:

• Device-state tests: 10 pass.
• On Fedora 44 with an iPad 6 Wi-Fi RAM payload: authenticated orchard exec, push and pull worked, including reconnecting after physical Lightning unplug/replug and live driver replacement.
• Both packages build as wheels. The full installed-wheel CLI suite ran 238 tests and has three failures outside this change: two older resolve test invocations omit the now-required --profile, and one local-receipt fixture rejects the virtualenv's lib64 symlink. The editable-environment run also exposed the older resolve test and installed-wheel isolation assumptions. No unrelated tests or command behavior were changed.